Zalando replaced shared edge routing for high-fan-out internal calls with an in-process load balancer that mirrors Skipper’s consistent-hash ring. They built a standalone JVM module for hash-parity routing, switched to a watch-based Kubernetes informer, and overhauled their CI/CD pipeline to safely roll out traffic ramps. The change cut latency spikes, reduced costs, and boosted deployment velocity.

• Replacing shared Skipper routing with an in-process client-side load balancer for internal fan-out calls eliminated latency spikes and noisy-neighbor ambiguity from shared infrastructure.
• The CSLB exactly replicates Skipper's consistent-hash ring (xxHash64, 100 virtual nodes) so both routers map product IDs identically, verified via unit tests and canary cache-hit parity.
• A Kubernetes informer with a two-second debounce coalesces pod churn into single ring updates, avoiding control-plane overload while keeping routing current.
• A refactored CI/CD pipeline cut build times from 21 to 12 minutes and removed 40+ manual steps, enabling faster iteration and safer traffic ramp-ups.